feat: Session drilldown feature to Performance & Errors charts - #539

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@web/app/pages/Project/tabs/Traffic/SessionsDrawer.tsx`:
- Around line 71-95: mapErrorSession is coercing ErrorAffectedSession into a
full SessionType by inserting synthetic zeros/defaults which produces misleading
UI; instead stop fabricating missing data: change mapErrorSession to return the
original ErrorAffectedSession shape (or a SessionType variant with the
truly-missing fields set to null/undefined) and update getResultSessions to
return the sessions as their real shape (e.g., union type SessionType |
ErrorAffectedSession) so the UI can render an error-specific row or display
"unknown" for missing fields rather than showing zero/default values; reference
mapErrorSession and getResultSessions when making these changes.
- Around line 193-207: The getErrorSessions branch calls fetchSessionsPage with
'getErrorSessions' but does not pass the active dashboard filters, causing
drilled sessions to ignore filtering; update the call in SessionsDrawer (the
branch using fetchSessionsPage('getErrorSessions', ...)) to include the current
filter payload (the same filter object used for the generic sessions query) so
the error-specific endpoint receives the same { period, from, to, timezone,
take, skip, ...filters, errorId } — alternatively, if the error endpoint cannot
accept filters, change the branch to call the generic sessions query (e.g.,
fetchSessionsPage('getSessions', ...)) when any dashboard filters are active so
drilled sessions respect the activeFilters.

In `@web/app/pages/Project/View/utils/chartPoint.ts`:
- Around line 48-49: The guard using eventRectsGroup.__clickAttached prevents
reattaching listeners and causes closures to capture stale
columns/onDataPointClick; replace the boolean flag with a versioned marker tied
to the current handler/data (for example store eventRectsGroup.__clickHandlerId
= `${columnsHash}:${onDataPointClickId}`) and only skip attaching when the
stored id matches the current one, or always remove existing listeners before
reattaching; update the logic in the block that sets
eventRectsGroup.__clickAttached (and the similar logic in lines 51-97) to use
this versioned marker or explicit removal so clicks use the latest columns and
onDataPointClick closures.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@backend/apps/cloud/src/analytics/analytics.service.ts`:
- Around line 6481-6489: The params object spreads filtersParams after explicit
keys which allows filter keys to inadvertently override critical query params;
change the construction of the params object so that ...filtersParams is spread
first and then explicit keys (pid, eid, groupFrom, groupTo, take, skip, ...) are
set afterwards (e.g., use { ...filtersParams, pid, eid, groupFrom, groupTo,
take, skip }) to ensure the explicit values in the params constant take
precedence over any entries produced by getFiltersQuery().